<html>
<head><meta charset="utf-8"><title>merged vscode settings · t-compiler/rust-analyzer · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/index.html">t-compiler/rust-analyzer</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html">merged vscode settings</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="196813202"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196813202" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Igor Matuszewski <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196813202">(May 07 2020 at 18:38)</a>:</h4>
<p><span class="user-mention" data-user-id="133169">@matklad</span> so I've been wanting to redesign the settings keys in the extension and was wondering what might be a good approach since we'd introduce a new swath of settings for rust-analyzer.</p>
<p>I've had a look at how other extensions do it and the approach I liked best was C#'s - e.g. it used tool-specific prefix without a common extension-wide prefix so <code>omnisharp.{path, autoStart, ...}</code> for OmniSharp-specific settings, <code>razor.{...}</code> for Razor-specific ones and <code>csharp.{...}</code> for regular/top-level settings.</p>
<p>This renders quite nicely in the new graphical UI for vscode settings and it' still discoverable by navigating to <code>Extensions &gt; C# &gt; Feature Contributions</code> where there's an entire list of them - obviously that's the same for 'C# configuration' section in the graphical UI for vscode settings.</p>
<p>What do you think?</p>



<a name="196813264"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196813264" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Igor Matuszewski <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196813264">(May 07 2020 at 18:39)</a>:</h4>
<p>I believe this has the benefit of retaining the existing <code>rust-analyzer.{...}</code> settings already used by the RA extension</p>



<a name="196813741"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196813741" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196813741">(May 07 2020 at 18:42)</a>:</h4>
<p>Hm, I think, in the end, I'd prefer to namespace just everything under <code>rust</code></p>



<a name="196813768"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196813768" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196813768">(May 07 2020 at 18:43)</a>:</h4>
<p>It's better for json completion, where you can do <code>rust.</code></p>



<a name="196813811"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196813811" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196813811">(May 07 2020 at 18:43)</a>:</h4>
<p>But using several different keys doesn't seem to bad to me either.</p>



<a name="196824330"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196824330" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Jeremy Kolb <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196824330">(May 07 2020 at 20:11)</a>:</h4>
<p>Isn't there already a <code>language.</code> convention for vscode?</p>



<a name="196862900"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/196862900" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Laurențiu <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#196862900">(May 08 2020 at 06:49)</a>:</h4>
<p>I'm strongly in favor of a <code>rust.</code> prefix, even if only for discoverability.</p>



<a name="197147297"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/197147297" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Igor Matuszewski <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#197147297">(May 11 2020 at 13:47)</a>:</h4>
<p><span class="user-mention silent" data-user-id="203366">Jeremy Kolb</span> <a href="#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/merged.20vscode.20settings/near/196824330">said</a>:</p>
<blockquote>
<p>Isn't there already a <code>language.</code> convention for vscode?</p>
</blockquote>
<p>The above settings such as <code>razor.</code> prefixed one come from official Microsoft's C# extension so I assume it depends on the team</p>



<a name="197147389"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/merged%20vscode%20settings/near/197147389" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Igor Matuszewski <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/merged.20vscode.20settings.html#197147389">(May 11 2020 at 13:48)</a>:</h4>
<p>there is also the <code>[$langId]: { &lt;settings_for_any_$langId_file&gt; }</code> which applies for anything activated for a specific language</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>